Securely Establishing Presence on Telecommunication Devices

ABSTRACT

In some embodiments, a user may associate a first communication type (e.g., Wi-Fi calling application) with a second communication type (e.g., standard ten-digit mobile telephone number), so that the user may have calls directed to an active communication type in a predetermined preference. In various embodiments, communication devices may become available (e.g., initiated) based on an activity of the user, such as by a location or proximity of the user, use of a device by the user, or for other reasons.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This patent application claims the benefit and priority to ProvisionalU.S. Patent Application No. 61/330,088, titled, “Connecting Devices to aWi-Fi Network with Authentication and Authorization”, filed on Apr. 30,2010, to the same inventors herein, the entire disclosure of which isincorporated by reference herein.

BACKGROUND

Today, people use electronic devices during a continually increasingportion of their day or week. For example, people use mobile telephonesto conduct business, personal computers to manage their finances, andmedia services to receive media for entertainment. Often, the servicesand functionality of multiple types of communication devices overlap.For example, a person may transmit electronic messages (email) via amobile telephone, a personal computer, a gaming console, and so forth,when these devices are configured properly. Each of these devices mayaccess unique accounts and/or share access to one or more of the sameaccounts. Often, people prefer to have access to various communicationsand data using multiple different devices, thus increasing convenienceand accessibility of information.

In telecommunications, people have many choices when conducting voicecalls. For example, voice calls may be made over wired telephone lines(i.e., fixed “land-line” calling), over mobile wireless networks (i.e.,cellular networks, digital mobile telephone networks), and over theInternet (e.g., voice-over Internet protocol (VoIP), etc.). Some or allof these types of communications may be routed through public switchedtelephone networks (PSTN), which allow a person to be contacted via anassociated address or telephone number. As people begin to use more thanone service, coordination and management of the services becomesincreasing important.

DESCRIPTION OF DRAWINGS

Non-limiting and non-exhaustive examples are described with reference tothe following figures. In the figures, the left-most digit(s) of areference number identifies the figure in which the reference numberfirst appears. The use of the same reference numbers in differentfigures indicates similar or identical items or features.

FIG. 1 is an illustrative environment showing Wi-Fi communications.

FIG. 2 is a flow diagram of an illustrative process of associatingmultiple communication devices and systems for cooperative operation.

FIG. 3 is a flow diagram of another illustrative process of associatingmultiple communication devices and systems for cooperative operation.

FIG. 4 is a flow diagram of an illustrative process of initiating anddeactivating devices for cooperative operation.

FIG. 5 is a block diagram of an illustrative computing device to enablecommunication via a secure network.

FIG. 6 is a block diagram of an illustrative telecommunications device.

DETAILED DESCRIPTION

As discussed above, people often use multiple electronic devices, whichmay perform functionality that overlaps with one another. For example, aperson may be able to perform a voice communication with a remotelylocated person via a mobile telephone call and/or a voice-over internetprotocol (VoIP) call. The VoIP call may be performed on any electronicdevice that has connectivity to the Internet, such as a computer, asmart phone (internet enabled and/or Wi-Fi telephone), an internetappliance, a gaming console, a set top box, and so forth.

In some embodiments, a user may associate a first communication type(e.g., Wi-Fi calling application) with a second communication type(e.g., standard ten digit mobile telephone number), so that the user mayhave calls directed to an active communication type in a predeterminedpreference. For example, a user may prefer to have calls forwarded fromthe ten-digit mobile number to a Wi-Fi-based mobile number when the userhas the Wi-Fi connection active, or when the Wi-Fi connection becomesactive. In various embodiments, communication devices may becomeavailable (or unavailable) based on an activity of the user, such as bya location or proximity of the user, use of a device by the user, or forother reasons.

The techniques, apparatus, and/or systems described herein may beimplemented in a number of ways. Example implementations are providedbelow with reference to the following figures.

Illustrative Environment

FIG. 1 is an illustrative environment 100 showing Wi-Fi communicationsin accordance with various embodiments of the disclosure. Theenvironment 100 includes a telecommunications device 102. Thetelecommunications device 102 may be a mobile telephone, a smart phone,a netbook, a personal computer, a personal digital assistant (PDA), atablet computer, a gaming console, or any other electronic devicecapable of enabling a user to perform voice, data, messaging, and/orInternet communications over a network. A user 104 may use thetelecommunications device 102 to place and receive voice communicationsand/or transmit data, messages, and/or interact with the Internet. Thevoice communications may be mobile telephone calls routed through amobile telephone networks 106 (e.g., 2G, 3G, other radio frequency (RF)wireless systems, etc.), Wi-Fi based calls, fixed land-line based calls,or other types of calls.

In some embodiments, the user 104 may employ a computing device 108 toassist (in whole or in part) with voice communications. The computingdevice 108 may be in communication with servers 110 via one or morenetwork(s) 112. Thus, the computing device 108 may exchange data, suchas voice communication data, with the servers 110 to enable voicecommunications between the user 104 and other users. In addition, thetelecommunications device 102 may connect to the servers 110 via thenetwork(s) 112 to exchange data with the servers (e.g., perform voicecommunications, etc.). In some instances the telecommunications device102 may communicate with the servers via Wi-Fi communications (via alocal access point (AP)), via the mobile telephone network (e.g., 3rdGeneration (3G) network, etc.) and so forth.

Once the user 104 establishes a Wi-Fi communication, such as via thetelecommunications device 102, the computing device 108, or anotherdevice, the user may desire to associate multiple communicationprocesses, devices, and systems for cooperative operation. For example,the user 104 may desire to receive all incoming calls via a Wi-Fiapplication whenever possible, and thus desire to have calls that aredirected to the user's mobile number (PSTN) to be routed to a Wi-Ficalling address, which may also be associated with a PSTN number.Techniques to securely associate various communication processes,devices, and/or systems are described below.

Once associated, calls may be routed to various devices that areassociated with each other based on various user-generated or defaultrules. In some embodiments, a location (proximity) or activity of theuser with respect to a telecommunications device may determine aparticular routing scheme. For example, when a user is driving his car,calls may be routed to a telecommunication device integrated in thecar's computer. Likewise, when the user is within a known Wi-Fi network,calls may be routed to the user's telecommunication device via a Wi-Ficalling application rather than being connected through a standardten-digit number associated with a mobile telephone or another callingdevice. For example, when the user is at home and is connected to aknown wireless network (e.g., Wi-Fi, Wi-Max, etc.), then calls initiallydirected to a mobile number may be redirected to the Wi-Fi callingapplication rather than the standard ten-digit number associated withthe mobile telephone.

Illustrative Configuration for Cooperative Operation

FIG. 2 is a flow diagram of an illustrative process 200 of associatingmultiple communication devices and systems for cooperative operation.The process 200 is illustrated as a collection of blocks in a logicalflow graph, which represent a sequence of operations that can beimplemented in hardware, software, or a combination thereof. Thecollection of blocks is organized under respective entities that mayperform the various operations described in the blocks. In the contextof software, the blocks represent computer-executable instructions that,when executed by one or more processors, perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the process. Otherprocesses described throughout this disclosure, in addition to process200, shall be interpreted accordingly.

The process 200 enables a first application, device, and/orcommunication type to be associated with a second application, device,and/or communication device. For example, the user 104 may use thetelecommunications device 102 to place and receive calls via the mobiletelephone network 106 and/or via a Wi-Fi calling application. The user104 may desire to have these two operations work in cooperation suchthat when the user is active with the Wi-Fi calling application,incoming calls that would normally be connected through the mobiletelephone network 106 are automatically routed (i.e., forwarded,directed, etc.) to the Wi-Fi calling application through the network112. The process 200 provides an illustrative process to configurecooperative operation of telecommunication devices while maintainingsecurity of the user's data (contact information, phone number, etc.).

At 202, a handset application may be installed on the telecommunicationsdevice 102 to enable Wi-Fi calling or other types of Internet or networkbased calls.

At 204, the handset application may generate a globally uniqueidentifier (GUID). The GUID may be used to connect to the handsetapplication, such as by routing a call initiated from another devicethrough the PSTN to the device running the handset application.

At 206, the handset application may request a mobile telephone number(MTN) (or other identifier/address, etc.) to be linked for cooperativeoperation, such as a ten-digit telephone number used by the PSTN. Insome embodiments, the handset application may securely read a mobilesubscriber integrated services digital network (MSISDN) and/or aninternational mobile subscriber identity (IMSI) from a subscriberidentity module (SIM) card of the telecommunications device 102.

At 208, the telecommunications device 102 transmits the GUID, the mobiletelephone number, and possibly other related information to the server110 via a secure communication (e.g., secure socket layer (SSL), etc.).For example, the telecommunications device 102 may transmit rulesassociated with using the GUID (e.g., when in network, between specifiedtimes, etc.), contact information such as the user's name and address,payment information, and so forth.

At 210, the servers 110 may receive the data and generate a one timepassword (OTP).

At 212, the servers 110 may transmit the OTP to the telecommunicationsdevice 102 at the mobile telephone number received at 206. The OTP maybe transmitted via simple message system (SMS), or by similar means(e.g. automated phone call, etc.). By transmitting the OTP back to thetelecommunications device 102, the servers 110 may prove (or verify)ownership and/or control over the telecommunications device 102, andthus authenticate use of this device by the user 104 for the cooperativeoperation. Similar techniques of authentication may also be used thataccomplish the same outcome.

At 214, the telecommunications device 102 receives the OTP from theservers 110 using the mobile telephone number transmitted at theoperation 206.

At 216, the OTP is inputted into the handset application (e.g., via akeypad) or otherwise received by the handset application (via memoryaccess).

At 218, the handset application creates an encrypted hash for the GUID,the mobile telephone number (MTN), and the OTP and sends the encryptedhash to the server.

At 220, the servers 110 receive and verify the encrypted hash. At 222,the servers 110 determine whether the encrypted hash is correct (e.g.,matches another hash that was previously created by the server using thesame or similar information, etc.). When the hash is correct (matchesGUID, MTN, OTP, etc.), then the servers 110 map the mobile telephonenumber to a SIP (Session Initiation Protocol) user identifier at 224(e.g., the GUID created above) and initiate cooperative operation (e.g.,routing, forwarding of calls, rerouting, etc.) at 226. In someembodiments, the cooperative operation may include rules of use, such asconditions under which to forward calls. However if the hash is notcorrect at 222, the telecommunications device 102 may be notified at 228and the cooperative operation may not be created. The telecommunicationsdevice 102 may also be notified with the cooperative operation issuccessfully implemented.

After successfully performing the process 200 to initiate cooperativeoperation at 226, no user input is required on subsequent handsetapplication launches. The servers 110 may automatically recognize theGUID and assume it is coming from the telecommunications device 102 (oranother device running the handset application) with the ten-digit phonenumber (MTN). In some embodiments, the servers 110 and handsetapplication may periodically negotiate new GUIDs on predefined intervalfor security purposes without any user interaction.

FIG. 3 shows another illustrative process 300 of associating multiplecommunication devices and systems for cooperative operation. The process300 uses another device 302 (“the other device 302”), which includes aGUID that the user 104 desires to associate with the mobile telephonenumber (MTB) of the telecommunications device 102. The other device 302may be a telecommunications device similar or identical to thetelecommunications device 102. The process 300 is described where thetelecommunications device 102 is used in the majority of the exchangesof data with the servers 110, however, in some embodiments, the otherdevice 302 may be used to perform a majority of the operations (e.g.,switching the roles of the telecommunication device 102 and the otherdevice 302, switching some operations, etc.).

At 304, the telecommunications device 102 may transmit the GUID, theMTN, and possibly other related information to the server 110 via asecure communication (e.g., secure socket layer (SSL), etc.).

At 306, the servers 110 may receive the data and generate a one timepassword (OTP).

At 308, the servers 110 may transmit the OTP to the other device 302 atthe GUID received at 304.

At 310, the other device 302 may receive the OTP, which may be displayedor otherwise communicated to the user 104 or directly to thetelecommunications device 102 via a signal (visual code wired/wirelesssignal, sound, etc.).

At 312, the telecommunications device 102 may receive the OTP, which wastransmitted from the server 110 to the other device 302. Thetelecommunications device 102 may receive the OTP by an alphanumericentry by the user 104 or by reading data from the other device 302 (scancode, record sound, receive signal, etc.). By receiving the code at theother device and then transferring the code to the telecommunicationsdevice, the user 104 proves possession of both devices and thus a rightor authority to associate the GUID and the MTN.

At 314, the handset application creates an encrypted hash for the GUID,the mobile telephone number (MTN), and the OTP and sends the encryptedhash to the server.

At 316, the servers 110 receive and verify the encrypted hash. At 318,the servers 110 determine whether the encrypted hash is correct (e.g.,matches another hash that was previously created by the server using thesame or similar information, etc.). When the hash is correct (matchesGUID, MTN, OTP, etc.), then the servers 110 map the mobile telephonenumber to a SIP (Session Initiation Protocol) user identifier at 320(e.g., the GUID created above) and initiate cooperative operation (e.g.,routing, forwarding of calls, rerouting, etc.) at 322. In someembodiments, the cooperative operation may include rules of use, such asconditions under which to forward calls. However if the hash is notcorrect at 318, the telecommunications device 102 may be notified at 324and the cooperative operation may not be created. The telecommunicationsdevice 102 may also be notified with the cooperative operation issuccessfully implemented.

FIG. 4 is a flow diagram of an illustrative process 400 of initiatingand deactivating telecommunication devices for cooperative operation.The process 400 may enable a determination of which device, application,or communication type is available to the user 102 based on dataassociated with the user (e.g., proximity location, activation,availability, etc.). The process may also include a protocol forfiguring out which device(s) to activate.

At 402, the telecommunications device 102 may initiate a communicationapplication (e.g., the handset application), either automatically ormanually. For example, a user may turn on the communication applicationusing a user interface (manual) or the communication application may beturned on by a triggering event (automatic), such as after detection ofan available wireless network, during a predetermined time period,during operation, during use by the user 104, proximity of the user(e.g., global positioning system (GPS) indicates the user is in hervehicle, etc.), and/or other events. As discussed in the process 200,the triggers (i.e., rules) may be created by the user and/or may bepredefined and communicated to the servers 110 during the process 200 orduring a later process to add or update rules.

The communication application may be in the telecommunications device102, which may be implemented in various different environments. Forexample, a first telecommunications device may be integrated in theuser's vehicle, a second telecommunications device may be integrated inthe user's alarm clock, a third telecommunications device may be coupledwith a television, and so forth. Each of these respectivetelecommunications devices may be configured for cooperative operationas discussed above in the process 200.

At 404, the respective telecommunications device (e.g., in the vehicle,alarm clock, the telecommunications device 102, etc.) may transmit aninitiation to the servers 110. The initiate may be a registrationmessage to indicate to the servers 110 that the telecommunicationsdevice 102 is available to receive calls for the user that are forwardedfrom a mobile telephone number and directed to the GUID.

At 406, the servers 110 may register the status of thetelecommunications device as active. At 408 the servers 110 may beginrouting (forwarding) communications to the active device (e.g., voicecalls, text messages, etc.). At 410, the servers 110 may transmit aconfirmation to the telecommunications device.

At 412, the telecommunications device 102 may use an application toconduct communications. For example, when the user 104 attempts to makean outbound call using the mobile telephone number via the mobiletelephone networks 106, the communication application may direct thetelecommunications device to use the network 112 to place the callrather than the mobile telephone networks.

At 414, the telecommunications device may determine whether thecommunication application is to be closed or otherwise deactivated. Whenuse is complete (e.g., the device is turned off, application is closed,rules or triggers are no longer satisfied, etc.), the telecommunicationsdevice may transmit a deactivation to the server at 416.

At 418, the server may update the status of the telecommunicationsdevice. At 420, the servers may end the routing that was initiated at408.

In an example implementation, the user may have a mobile telephonenumber (MTN), a land-line telephone number (LLTN), and various VoIPnumbers (GUID, etc.) associated with various telecommunication devicesthat the user interacts with during the day. When the user drives towork in her car, calls to the MTN or LLTN may be forwarded to thevehicle telecommunication device via the process 400 based on aninitiation caused by the use of the vehicle, proximity of the user, orother triggers/rules, etc. When the user parks the vehicle and enters abuilding for work, the vehicle telecommunications device may bedeactivated and calls may then be resumed by other telecommunicationsdevices, such as a mobile telephone with the MTN.

In another example, the telecommunications device 102 may be implementedin an alarm clock. When the user is near the alarm clock (as detected bya proximity detector), during a predetermined period of time, and/orbased on other triggers, the alarm clock may be initiated at theoperation 402 and operate in accordance with the process 400 untiloperation is terminated at 416 (e.g., the user leave the proximity, theperiod of time expires, and so forth.).

In still another example, the telecommunications device 102 may beimplemented in a television, set-top box, receiver, or other multimediadevice. For example, when the user is watching the television, thetelevision may be initiated at the operation 402 and operate inaccordance with the process 400 until the cooperative operation isterminated at the operation 416.

In some embodiments, the application 402 may also be initiated when thetelecommunication device detects presence of the network 112, such aswhen the user is home and the telecommunications device logs on to aknown network wireless network, such as a local area network (LAN), widearea network (WAN), or other type of network other than the mobiletelephone network 106. Thus, when the telecommunications device 102detects the known network, then the communication application may beinitiated at 402. The telecommunications device 102 may operate inaccordance with the process 400 until operation is terminated at 416,such as when the telecommunications device 102 is disconnected from theknown network or otherwise losses a signal associated with the knownnetwork or upon occurrence of another terminating event.

Illustrative Computing Devices

FIG. 5 is a block diagram of an illustrative computing device to enablecommunication via a secure network. In various embodiments, computingdevice 500 (such as the computing device 108) may include at least oneprocessing unit 502 and system memory 504. Depending on the exactconfiguration and type of computing device, system memory 504 may bevolatile (such as RAM), non-volatile (such as ROM, flash memory, etc.)or some combination of the two. System memory 504 may include anoperating system 506, one or more program modules 508, and may includeprogram data 510.

Computing device 500 may also include additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG. 5by storage 512. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory 504 and storage 512 are all examples of computer-readable storagemedia. Computer-readable storage media includes, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by computing device 500.Any such computer-readable storage media may be part of device 500.

In various embodiment, any or all of system memory 504 and storage 512may store programming instructions which, when executed, implement someor all of the above-described operations of the server 110 and/or thecomputing device 108.

Computing device 500 may also have input device(s) 514 such as akeyboard, a mouse, a touch-sensitive display, voice input device, etc.Output device(s) 516 such as a display, speakers, a printer, etc. mayalso be included. These devices are well known in the art and need notbe discussed at length here.

Computing device 500 may also contain communication connections 518 thatallow the device to communicate with other computing devices 520.

FIG. 6 is a block diagram of an illustrative telecommunications device600 in accordance with various embodiments. As shown, thetelecommunications device 600 (such as the telecommunications device102) may include a memory 602, the memory storing an application, OS,and data 604. For example, the application or data 604 may include thehandset application and/or the communication application discussed withrespect to the processes 200 and 300, respectively. Thetelecommunications device 600 further includes processor(s) 606,interfaces 608, a display 610, transceivers 612, output devices 614,input devices 616, and drive unit 618 including a machine readablemedium 620.

In various embodiments, memory 602 generally includes both volatilememory and non-volatile memory (e.g., RAM, ROM, EEPROM, Flash Memory,miniature hard drive, memory card, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other medium).Additionally, in some embodiments, memory 602 includes a SIM (subscriberidentity module) card, which is a removable memory card used to identifya user of the telecommunications device 600 to a service providernetwork. Memory 602 can also be described as computer storage media andmay include volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data

The applications, OS, and data 604 stored in memory 606 are also shownin FIG. 1 and described above in detail with reference to that figure.

In some embodiments, the processor(s) 606 is a central processing unit(CPU), a graphics processing unit (GPU), or both CPU and GPU, or otherprocessing unit or component known in the art.

In various embodiments, the interfaces 608 are any sort of interfacesknown in the art. Interfaces 608 include any one or more of an Ethernetinterface, wireless local area network (LAN) interface, a near fieldinterface, a DECT chipset, or an interface for an RJ-11 or RJ-46 port.The a wireless LAN interface can include a Wi-Fi interface or a Wi-Maxinterface, or a Bluetooth interface that performs the function oftransmitting and receiving wireless communications using, for example,the IEEE 802.11, 802.16 and/or 802.20 standards. For instance, thetelecommunications device 600 can use a Wi-Fi interface to communicatedirectly with a nearby device. The near field interface can include aBluetooth® interface or radio frequency identifier (RFID) fortransmitting and receiving near field radio communications via a nearfield antenna. For example, the near field interface may be used forfunctions, as is known in the art, such as communicating directly withnearby devices that are also, for instance, Bluetooth® or RFID enabled.A reader/interrogator may be incorporated into telecommunications device600.

In various embodiments, the display 610 is a liquid crystal display orany other type of display commonly used in telecommunication devices.For example, display 610 may be a touch-sensitive display screen, andcan then also act as an input device or keypad, such as for providing asoft-key keyboard, navigation buttons, or the like.

In some embodiments, the transceivers 612 include any sort oftransceivers known in the art. For example, transceivers 612 may includea radio transceiver and interface that performs the function oftransmitting and receiving radio frequency communications via anantenna. The radio interface facilitates wireless connectivity betweenthe telecommunications device 600 and various cell towers, base stationsand/or access points.

In some embodiments, the output devices 614 include any sort of outputdevices known in the art, such as a display (already described asdisplay 610), speakers, a vibrating mechanism, or a tactile feedbackmechanism. Output devices 614 also include ports for one or moreperipheral devices, such as headphones, peripheral speakers, or aperipheral display.

In various embodiments, input devices 616 include any sort of inputdevices known in the art. For example, input devices 616 may include amicrophone, a keyboard/keypad, or a touch-sensitive display (such as thetouch-sensitive display screen described above). A keyboard/keypad maybe a push button numeric dialing pad (such as on a typicaltelecommunication device), a multi-key keyboard (such as a conventionalQWERTY keyboard), or one or more other types of keys or buttons, and mayalso include a joystick-like controller and/or designated navigationbuttons, or the like.

The machine readable medium 620 stores one or more sets of instructions(e.g., software) embodying any one or more of the methodologies orfunctions described herein. The instructions may also reside, completelyor at least partially, within the memory 602 and within the processor606 during execution thereof by the telecommunications device 600. Thememory 602 and the processor 606 also may constitute machine readablemedia 620.

CONCLUSION

Although structural features and/or methodological acts are describedabove, it is to be understood that the appended claims are notnecessarily limited to those features or acts. Rather, the features andacts described above are disclosed as example forms of implementing theclaims.

1. A method comprising: receiving a message from a telecommunicationsdevice, the message including at least a mobile telephone number and aglobally unique identifier (GUID) for the telecommunications device thatidentify communication paths available for use by the telecommunicationsdevice, the message received by a server using a communication pathassociated with the GUID; transmitting a code to the telecommunicationsdevice in response to the message using a communication path associatedwith the mobile telephone number; receiving a hash from thetelecommunications device that is based at least in part on the code andused to authenticate a relationship between the mobile telephone numberand the GUID; and mapping the mobile telephone number to the GUID whenthe hash includes the code, the mapping to create a cooperativeoperation that forwards communications initially directed to the mobiletelephone number to be directed to the GUID.
 2. The method as recited inclaim 1, wherein the message further includes at least one rule thatprovides conditions which, when satisfied, result in implementation ofthe cooperative operation.
 3. The method as recited in claim 1, furthercomprising receiving a registration message from the telecommunicationsdevice to initiate the cooperative operation.
 4. The method as recitedin claim 3, further comprising routing calls that are initially directedto the mobile telephone number to be directed to the GUID following aregistration of the telecommunications device.
 5. The method as recitedin claim 3, further comprising transmitting a confirmation to thetelecommunications device that the cooperative operation is active. 6.The method as recited in claim 4, further comprising terminating thecooperative operation after receipt of a termination request by thetelecommunications device to stop redirecting and begin to receive callsfor the mobile telephone using the mobile telephone network.
 7. Amethod, comprising: creating a globally unique identifier (GUID)associated with a communication path available by the telecommunicationsdevice that is different than a communications path that is associatedwith a mobile telephone number; transmitting a message to a server thatincludes at least the mobile telephone number and the GUID using thecommunication path associated with the GUID; receiving a code from theserver using the communication path associated with the mobile telephonenumber; transmitting a hash to the server that is based at least in parton the code, the mobile telephone number, and the GUID, the hash toauthenticate a relationship between the mobile telephone number and theGUID and map, by a server, the mobile telephone number and the GUID toinitiate cooperative operation; and receiving a call directed to themobile telephone number and forwarded to the GUID based at least in parton the cooperative operation initiated by the server.
 8. The method asrecited in claim 7, wherein the communication path associated with theGUID is a Voice over Internet Protocol (VoIP) communication path.
 9. Themethod as recited in claim 7, further comprising transmitting aregistration message from the telecommunications device to initiate thecooperative operation.
 10. The method as recited in claim 9, wherein thetransmitting the registration message occurs in response to detectingavailability of the communication path associated with the GUID.
 11. Themethod as recited in claim 9, wherein the transmitting the registrationmessage occurs in response to powering on the telecommunications device.12. The method as recited in claim 9, wherein the transmitting theregistration message occurs in response to at least one of a detectionof user interaction with the telecommunications device, a predeterminedproximity of a user to the telecommunications device, or a predeterminedtime.
 13. The method as recited in claim 7, further comprising receivinga confirmation from the server that the cooperative operation is active.14. The method as recited in claim 7, further comprising routing callsinitiated on the telecommunications device using the communication pathassociated with the mobile telephone number through the communicationpath associated with the GUID while the cooperative operation is active.15. The method as recited in claim 7, further comprising transmitting atermination message to the server to terminate the cooperative operationand begin using the communication path associated with the mobiletelephone number.
 16. One or more computer-readable storage mediastoring computer-executable instructions that, when executed on one ormore processors, performs acts comprising: receiving a message thatincludes at least a mobile telephone number of a first device and aglobally unique identifier (GUID) for a second device, each having aseparate communication path available to exchange information with aserver, the message received by the server using a communication pathassociated with the mobile telephone number from the first device;transmitting a code to the second device using a communication pathassociated with the GUID; receiving a hash from the first device that isbased at least in part on the code and used to authenticate arelationship between the mobile telephone number and the GUID; andmapping the mobile telephone number to the GUID when the hash includesthe code to create cooperative operation that forwards communicationsinitially directed to the first device to be directed to the seconddevice using the GUID.
 17. The one or more computer-readable storagemedia as recited in claim 16, wherein the acts further comprisereceiving a registration from the second device to initiate thecooperative operation.
 18. The one or more computer-readable storagemedia as recited in claim 17, wherein the receiving occurs in responseto detecting availability of the communication path associated with theGUID.
 19. The one or more computer-readable storage media as recited inclaim 17, wherein the receiving occurs in response to powering on thesecond device.
 20. The one or more computer-readable storage media asrecited in claim 16, wherein the second device at least one of atelevision, set-top box, audio receiver, or an alarm clock.